fix(ci): skip docs build in release workflow#262
Conversation
Docs are built separately on Vercel, so excluding them from release workflow to avoid fumadocs-mdx generation failure Co-authored-by: Cursor <cursoragent@cursor.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
sadmann7
changed the title
There was a problem hiding this comment.
Pull request overview
This PR fixes a failing release workflow by excluding the docs package from the build step. The docs package is a Next.js application that requires fumadocs-mdx content generation during build, which was causing failures. Since docs are deployed separately on Vercel, they don't need to be built in the release workflow. This change aligns the release workflow with the existing CI workflow approach.
Changes:
- Modified release workflow to use
pnpm turbo build --filter=!docsinstead ofpnpm build - Updated step name in CI workflow from "Build packages (excluding docs)" to "Build packages"
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| .github/workflows/release.yml | Added --filter=!docs to exclude docs from build in release workflow |
| .github/workflows/main.yml | Simplified step name by removing "(excluding docs)" suffix |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - uses: ./.github/setup | ||
|
|
||
| - name: Build packages (excluding docs) | ||
| - name: Build packages |
There was a problem hiding this comment.
The step name "Build packages" is inconsistent with the naming pattern used for other filtered steps in this workflow. The test step (line 72) uses "Test packages (excluding docs)" and the typecheck step (line 86) uses "Typecheck packages (excluding docs)". For consistency, this should either be "Build packages (excluding docs)" to match the other steps, or all step names should be simplified to remove the "(excluding docs)" suffix.
| - name: Build packages | |
| - name: Build packages (excluding docs) |
Summary
Context
The release workflow was failing at the docs:generate:content step. Since docs are built separately on Vercel during deployment, there's no need to build them in the release workflow.
Changes